Repository navigation
fix: fail CI when required QA tools or configurations are missing - #6
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Missing required QA tools or configuration previously produced successful SKIP results in CI. CI now fails closed by default, and repository Composer scripts invoke strict QA explicitly. Local non-strict use remains an explicit diagnostic option; disabled optional tools are handled separately from missing mandatory checks.
Stable dependencies require the published Coding Standards1.1.1 SQL rule, and export rules preserve the executable/runtime resources while excluding development artifacts. A weekly dependency canary uses the reviewed immutable reusable workflow.
Validation: doctor, syntax, PHPCS and PHPStan passed; PHPUnit 28 tests / 145 assertions. Independent failure probes cover missing tools/configuration and CI strict behavior. Native actionlint and exact-commit distribution validation passed. Candidate version
v0.1.2; historical tags are retained.